System and method for optimized idle and active state transitions of user equipment in a network environment

ABSTRACT

An example method is provided in one example embodiment and may include determining that a user equipment (UE) is approximately stationary for a threshold period of time within a particular geographic area based, at least in part, on a radio access network (RAN) node to which the UE is attached; notifying the UE that the UE has been associated with the particular geographic area; and transitioning the UE into an idle mode from an active mode, wherein the transitioning is performed without notifying a core network that the UE has transitioned to the idle mode. Determining that the UE is approximately stationary can include monitoring mobility signaling from the UE and comparing an amount of time that the UE has been attached to the RAN node with a threshold period of time. The core network can be notified when the UE moves out of the particular geographic area.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefit of priority under 35 U.S.C. § 119(e)to U.S. Provisional Application Ser. No. 62/337,174, entitled “SYSTEMAND METHOD TO FACILITATE OPTIMIZED IDLE AND ACTIVE STATE TRANSITIONS INA NETWORK ENVIRONMENT,” filed May 16, 2016.

TECHNICAL FIELD

This disclosure relates in general to the field of communications and,more particularly, to a system and method for optimized idle and activestate transitions of user equipment in a network environment.

BACKGROUND

Networking architectures have grown increasingly complex incommunication environments. As the number of mobile subscribersincreases, efficient management of messaging and signalingcommunications between user equipment and core network resources becomescritical. Messaging communications can include data and controlcommunications at the application level, whereas signalingcommunications typically involve control communications with the networkproviding connectivity for data services. Messaging and signalinginteractions that occur when a user equipment transitions between idleand active mode can consume system resources that could otherwise beused to provide other services and/or improve user experience. When idleand active mode transitions occur across multiple user equipment servicein a communication system, the compounded effects of such transitionscan create network congestion and/or lead to suboptimal use of networkresources. Accordingly, there are significant challenges in managingidle and active mode transitions of user equipment in a networkenvironment.

BRIEF DESCRIPTION OF THE DRAWINGS

To provide a more complete understanding of the present disclosure andfeatures and advantages thereof, reference is made to the followingdetailed description, taken in conjunction with the accompanyingfigures, wherein like reference numerals represent like parts, in which:

FIG. 1 is a simplified block diagram illustrating a communication systemto facilitate optimized idle and active state transitions of userequipment in a network environment according to one embodiment of thepresent disclosure;

FIG. 2 is a simplified interaction diagram illustrating example detailsthat can be associated with optimizing idle and active state transitionsof user equipment in a network environment in accordance with onepotential embodiment;

FIG. 3 is a simplified interaction diagram illustrating other exampledetails that can be associated with optimizing idle and active statetransitions of user equipment in a network environment in accordancewith one potential embodiment;

FIG. 4 is a simplified interaction diagram illustrating yet otherexample details that can be associated with optimizing idle and activestate transitions of user equipment in a network environment inaccordance with one potential embodiment;

FIG. 5 is a simplified interaction diagram illustrating yet otherexample details that can be associated with optimizing idle and activestate transitions of user equipment in a network environment inaccordance with one potential embodiment; and

FIGS. 6-8 are simplified block diagrams illustrating example detailsthat can be associated with various potential embodiments of thecommunication system.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

Overview

A method is provided in one example embodiment and may includedetermining that a user equipment (UE) is approximately stationary for athreshold period of time within a particular geographic area based, atleast in part, on a radio access network (RAN) node to which the UE isattached; notifying the UE that the UE has been associated with theparticular geographic area; and transitioning the UE into an idle modefrom an active mode, wherein the transitioning is performed by the RANnode without notifying a core network that the UE has transitioned tothe idle mode. In at least one instance, the method can further includestoring context information for the UE at the RAN node when the UEtransitions to the idle mode. In various instances, the particulargeographic area can be associated with at least one of: an identity ofthe RAN node; and a cell identity for the RAN node.

In one instance, determining that the UE is approximately stationary canfurther include monitoring mobility signaling from the UE to determinean amount of time that the UE has been attached to the RAN node; andcomparing the amount of time with the threshold period of time todetermine when the amount of time is greater than or equal to thethreshold period of time.

In some instances, the method can further include notifying the corenetwork when the UE moves out of the particular geographic area. In someinstances, the notifying can include notifying an access controllerwithin the core network via Non-Access Stratum (NAS) signaling sent fromthe UE to the access controller.

In some cases, the method can further include transitioning the UE to anactive state for at least one of: sending downlink data or signaling tothe UE; and receiving uplink data or signaling from the UE. In at leastone case, the transitioning can be performed without signaling the corenetwork that the UE has been transitioned from the idle mode to theactive mode. In at least one case, the transitioning includes onlysetting up radio bearers for the UE.

Example Embodiments

For purposes of understanding certain embodiments of systems and methodsdisclosed herein, it is important to appreciate the technologies anddata that may be associated with network communications. The followingfoundational information may be viewed as a basis from which the presentdisclosure may be properly explained.

Architectures that facilitate network communications generally rely uponthree basic components: a data-plane, a control-plane, and amanagement-plane. The data-plane carries user traffic, while thecontrol-plane and the management-plane serve the data-plane. As referredto herein in this Specification, the term ‘plane’ can refer to aseparation of traffic that can traverse a network. As referred to hereinin this Specification, the terms ‘user-plane’, ‘data-plane’, ‘userdata-plane’ and variations thereof can be used interchangeably.

In some architectures, Software Defined Network (SDN) concepts can beapplied to control-plane and user plane elements or nodes in order tofacilitate a split control and user-plane (split C/U-plane)architecture. Generally, SDN is an approach to building computernetworks, networking equipment and software that separates and abstractsthe control-plane and data-plane of networking systems. SDN decouplesthe control-plane elements or nodes that make decisions about wheretraffic is sent from the underlying data-plane elements or nodes thatforward traffic to a selected destination. SDN allows networkadministrators, operators, etc. to manage network services throughabstraction of lower level functionality into a virtualized networkenvironment.

As referred to herein in this Specification, the terms ‘virtualmachine’, ‘virtualized network function’, ‘virtualized networkfunctionality’ and variations thereof can encompass an emulation of acomputer system and/or computing platform operating based on thecomputer architecture and functions of a real or hypothetical computer,with particular embodiments involving specialized hardware, software, ora combination of both. In various embodiments, a virtualized networkfunction (VNF), a virtual machine (VM), virtualized functionality and/orany virtualized network controller, module, node, aggregator,combinations thereof or the like as described herein may execute via ahypervisor-based virtualization or a container-based virtualization of aserver (e.g., blade server, rack server, stand-alone server) using theserver's hardware (e.g., processor and memory element) and/or operatingsystem for a given virtualized network environment.

In some cases, VNF(s) can be configured to perform one or morespecialized operations within a network environment and one or moreinstances of the configured VNF(s) can be instantiated in order toexecute the one or more specialized operations. In some instances,VNF(s) can include one of more virtualized network function components(VNFCs). In some embodiments, a VNFC can be an internal component of aVNF, which can provide a VNF provider a defined subset of that VNF'sfunctionality via VNFC instantiation (VNFCI). In some embodiments,operations or functionality associated with a RAN and/or a core networkcan be configured to be executed via one or more VNFs and/or VNFCsand/or one or more Physical Network Functions (PNFs) to realize avirtualized RAN (vRAN) and/or a virtualized core network architecture. APNF is typically associated with a hardware radio head, which can beconfigured with one or more transmitters and receivers (and otherassociated hardware and software functionality) in order to facilitateover-the-air (OTA) Radio Frequency (RF) communications with one or moreuser equipment (UE).

In many 3rd Generation Partnership Project (3GPP) architectures such asLong Term Evolution (LTE) architectures, transitions between idle andactive modes by user equipment (UE) may arguably be the most frequentlyused procedure by UE attached to an LTE communication network. In someof the networks, it has been found that the Service Request procedure(e.g., transition from idle to active mode) is performed by each UEapproximately every two minutes. Current processes for the ServiceRequest procedure, as defined by 3GPP standards, are described in 3GPPTechnical Specification (TS) 23.401, Section 5.3.4. In general, thecurrent Service Request procedure includes the following signaling:paging a given UE over the radio interface; UE to Mobility ManagementEntity (MME) Non-Access Stratum (NAS) messaging for requesting radioresources by the UE; UE to evolved NodeB (eNB) Radio Resource Control(RRC) messaging for establishing the radio resources; MME to ServingGateway (SGW) General Packet Radio Service (GPRS) Tunneling Protocolversion 2 (GTPv2) messaging to inform the S1 user data-plane (S1U)tunnel endpoint identity (TEID) of the eNB to the SGW; and, in splitC/U-plane architectures, SGW control-plane element (SGW-C) to SGW userdata-plane element (SGW-U) messaging to program downlink data flows withthe appropriate TEID of the eNB.

Any optimization in the Service Request procedure would likely lead tosome gain in reducing one or more of the above messaging/signaling on aper-UE basis. Multiplying such a gain over the large number of UEs thatare typically attached to a network and that can be performing theService Request procedure approximately every two minutes would likelyresult in large signaling savings between the UE and core network andwithin the core network.

Moreover, in a split C/U-plane architecture, frequently altering a givenUE's flow (e.g., when the UE becomes idle the flow is removed and thenagain when the UE becomes active a new flow is added) will likely placehigher transaction per second (TPS) requirements over the interfacebetween control- and user-plane elements or nodes and, in turn, it maylead to performance (e.g., throughput) deterioration in the forwarding(e.g., data) plane. Thus, reducing Service Request procedure messagingwill also likely help in efficiently achieving split C/U-planearchitectures.

Although it is desirable to keep a UE in an active mode, doing so is notpossible as it would cause a UE battery drainage issue, it would resultin radio resources potentially unnecessarily being reserved at the eNBto which the UE was attached and it would prevent the eNB to which theUE is connected from multiplexing radio resources among a large numberof UEs. To summarize, the Service Request procedure to transitionbetween idle and active mode cannot be alleviated. However, it isnonetheless desirable to minimize the signaling due to the ServiceRequest procedure so as to make the procedure lighter (e.g., in terms oftotal number of messaging/signaling) as compared to the manner in whichthe current Service Request procedure is provided in currentdeployments. As referred to herein, the terms ‘active mode’, ‘activestate’ and ‘RRC active’ mode or state can be used interchangeably andthe terms ‘idle mode’, ‘idle state’ and ‘RRC idle’ mode or state canalso be used interchangeably.

In accordance with at least one embodiment of the present disclosure, acommunication system 100 as shown in FIG. 1 illustrates an architecture,which can overcome the aforementioned shortcomings (and others) byproviding a system and method that can facilitate optimized idle andactive state transitions of user equipment in a network environment. Thearchitecture of communication system 100 shown in the embodiment of FIG.1 includes a Radio Access Network (RAN) 110 including a RAN node 114,which can provide a communication interface to one or more usersoperating user equipment (UE) 112 and a core network (CN) 120, which caninclude an access controller 122, one or more data-plane node(s) 124 andone or more control-plane node(s) 126, and one or more packet datanetwork(s) PDN(s) 130. The embodiment of FIG. 1 illustrates an examplesplit C/U-plane architecture.

UE 112 can interface with RAN node 114 via an over-the-air (OTA)interface, such as, for example, a Radio Frequency (RF) interface. RANnode 114 can interface via a control-plane interface with accesscontroller 122, which can interface via one or more control-planeinterface(s) with one or more control-plane node(s) 126. Thecontrol-plane interface between RAN node 114 can be an S1 ApplicationProtocol (S1-AP) interface. Control-plane node(s) 126 can furtherinterface via one or more control-plane interface(s) with one or moredata-plane node(s) 124. RAN node 114 can further interface via one ormore data-plane interface(s) with one or more data-plane node(s) 124 viaone or more S1 user-plane (S1-U) interfaces. One or more data-planenode(s) 124 can further interface with one or more PDN(s) 130. Invarious embodiments, one or more PDN(s) can include an internet, webserver(s), enterprise network, an Internet Protocol (IP) MultimediaSubsystem (IMS), combinations thereof or the like.

Each of the elements of FIG. 1 may couple to one another through simpleinterfaces (as illustrated) or through any other suitable connection(wired or wireless), which provides a viable pathway for networkcommunications. Additionally, any one or more of these elements may becombined or removed from the architecture based on particularconfiguration needs. Communications in a network environment arereferred to herein as ‘messages’, ‘messaging’ and/or ‘signaling’, whichmay be inclusive of packets. Generally, signaling is referred to inreference to control-plane packets while messaging can be referred to inreference to control-plane or data-plane packets exchanged forcommunications at the application level. A packet is a formatted unit ofdata and can contain both control information (e.g., source anddestination address, etc.) and data, which is also known as payload. Insome embodiments, control information can be included in headers andtrailers for packets. Messages can be sent and received according to anysuitable communication messaging protocols. Suitable communicationmessaging protocols can include a multi-layered scheme such as the OpenSystems Interconnection (OSI) Model, or any derivations or variantsthereof. The terms ‘data’, ‘information’ and ‘parameters’ as used hereincan refer to any type of binary, numeric, voice, video, textual orscript data or information or any type of source or object code, or anyother suitable data or information in any appropriate format that can becommunicated from one point to another in electronic devices and/ornetworks. Additionally, messages, requests, responses, replies, queries,etc. are forms of network traffic and, therefore, may comprise one ormore packets.

In various embodiments, communication system 100 can represent a seriesof points or nodes of interconnected communication paths (wired orwireless) for receiving and transmitting packets of information thatpropagate through communication system 100. In various embodiments,communication system 100 can be associated with and/or provided by asingle network operator or service provider and/or multiple networkoperators or service providers. In various embodiments, communicationsystem 100 can include and/or overlap with, in whole or in part, one ormore packet data networks, such as, for example, PDN(s) 140.Communication system 100 may offer communicative interfaces betweenvarious elements of communication system 100 and may be any local areanetwork (LAN), wireless local area network (WLAN), metropolitan areanetwork (MAN), wide area network (WAN), virtual private network (VPN),Radio Access Network (RAN), virtual local area network (VLAN),enterprise network, Intranet, extranet, or any other appropriatearchitecture or system that facilitates communications in a networkenvironment.

In various embodiments, communication system 100 may implement userdatagram protocol/Internet Protocol (UDP/IP) connections and/ortransmission control protocol/IP (TCP/IP) communication languageprotocol in particular embodiments of the present disclosure. However,communication system 100 can alternatively implement any other suitablecommunication protocol, interface and/or standard, proprietary and/ornon-proprietary, for transmitting and receiving messaging and/orsignaling. Other protocols, interfaces and/or communication standardsthat can be used in communication system 100 can include 3GPPDiameter-based protocols, Remote Authentication Dial-In User Service(RADIUS) protocols, Authentication, Authorization and Accounting (AAA)signaling, a service gateway interface (SGi), a Terminal Accesscontroller access-control system (TACACS), TACACS+, Proxy Mobile IPversion 6 (PMIPv6), Proxy Mobile IP version 4 (PMIPv4), ExtensibleMessaging and Presence Protocol (XMPP), General Packet Radio Service(GPRS) Tunneling Protocol (GTP) (version 1 or version 2), Generic RouteEncapsulation (GRE), Ethernet over GRE (EoGRE), etc. In variousembodiments, AAA signaling can include signaling exchanges facilitatedvia Diameter, RADIUS, Extensible Messaging and Presence Protocol (XMPP),Simple Object Access Protocol (SOAP), SOAP over Hypertext TransferProtocol (HTTP), Representational State Transfer (REST), combinationsthereof or the like.

During operation, in at least one embodiment, communication system 100can be configured such that when UE 112 transitions into an idle mode,only radio resources (e.g., bearer(s)) for the UE are released while theRAN node 114 keeps S1-AP and S1-U sessions active for the UE as long asthe UE stays within the RAN node's coverage area. The access controller122 will not be notified of the UE's transition to idle mode.Subsequently, if downlink data for the UE arrives at the RAN node, onlythe radio resources (e.g., bearer(s)) will need to be reestablishedwhile other messaging typically needed for the current Service Requestprocedure can be avoided. Thus, by reducing the overall messagingrequirement of a Service Request (e.g., reducing the total number ofmessages needed for performing a Service Request), embodiments of thepresent disclosure provide a system and method for an optimized ServiceRequest procedure that is light and efficient compared to the currentService Request procedure provided in 3GPP standards. Further, for splitC/U-plane architectures, frequent modification of the UE's flow in theforwarding plane can be avoided for idle and active mode transitions.

At a minimum, a default bearer, as defined in 3GPP standards, isestablished for a given UE upon initial attachment of the UE to a givenRAN node. In some instances, one or more dedicated bearers can beestablished for a given UE for one or more specialized services orapplications provided to the UE such as, for example, a Voice over LTE(VoLTE) session, a data session, a Voice over IP (VoIP) session, agaming session, a video session, combinations thereof or the like. Ingeneral, a bearer for a given UE is associated with the followinginformation and/or parameters within the EPC: 1) an IP address for theUE, which can be allocated from a pool of IP addresses via Dynamic HostConfiguration Protocol (DHCP), Stateless Address Auto-configuration(SLAAC), etc.; 2) an IP address for an EPC node for a given PDNconnection for the UE; and 3) at least one GTP user-plane (GTP-U) bearertunnel extending between a PGW/PGW-U and a SGW/SGW-U and at least oneGTP-U bearer tunnel extending from the SGW/SGW-U to the RAN node towhich the UE is connected (e.g., if the UE is in a CONNECTED mode orstate). In LTE architectures, a bearer can be identified using an EPSBearer Identity (EBI).

To facilitate optimized idle and active mode transitions for theoptimized Service Request procedure provided by embodiments discussedherein, it is beneficial to consider the general behavior of a given UE(e.g., the behavior of the human user/subscriber associated with thegiven UE). In general, a UE/subscriber exhibits peculiar cycles, whichcan include, but not be limited to: ‘mobile’, ‘stationary and consumingdata’ or ‘approximately stationary and consuming data’, and ‘mobile’again.

For example, consider that a person travels to an office (e.g., ismobile) and then consumes data at the office (e.g., is approximatelystationary and consuming data), the person travels from the office to ahome (e.g., is mobile again) and then consumes data (e.g., is stationaryagain and consuming data), a person goes to a restaurant (e.g., ismobile) and spends most of the evening in a vicinity of the restaurantand consumes data (e.g., is approximately stationary and consumingdata), a person goes to a shopping mall, sporting event, arena, etc. andspends an extended period of time involved in various activities in avicinity of the mall, event, arena, etc. and consumes data during thistime (e.g., is approximately stationary and consuming data). Thus, ingeneral, with the exception for cases in which human subscribers areconsuming data on a moving train, bus, plane, etc., subscribers areoften consuming data while stationary. The terms ‘stationary’ or‘approximately stationary’, as referred to herein, are meant to refer toa UE that: remains within the coverage area of a particular RAN node,remains within an area covered by one or more cells provided by aparticular RAN node and/or remains within an area covered by multiplespecific RAN nodes and/or multiple cells of multiple specific RAN nodesfor a certain threshold period of time.

Although a UE, when connected to the core network 120 can assumed to beunder the coverage of “some” RAN node, a determination of stationary orapproximately stationary can be determined based on the UE remaining ina particular area of a particular RAN node, RAN nodes, cell areas, etc.as noted above, for a certain threshold period of time. In variousembodiments, a threshold period of time that can be used to determinewhether a UE is stationary/approximately stationary or non-stationarycan include a number of minutes, hours, days, combinations thereof orthe like, as configured by a network operator or service provider.

For stationary or approximately stationary UEs, it is possible to reachthem for delivery of downlink data by first paging the last cellidentifier (ID) reported by the UE to avoid paging in a wider area tofind the UE. An optimized Service Request procedure can be providedbased on such a paging principle.

Consider an operational example involving UE 112. During operation, inat least one embodiment, the network (e.g., the RAN node, accesscontroller, combinations thereof or the like) can monitor the UE'slocation for a duration of time, which can be compared against athreshold period of time that can be set to indicate when a UE isstationary or approximately stationary. If the monitored duration oftime for a given UE within a particular geographic area is greater thanor equal to a given threshold period of time, the network can determinethat the UE is stationary or approximately stationary for the particulargeographic area.

In various embodiments, a UE's location can be determined based onlocation updates or other mobility signaling received from the UE suchas, for example, Tracking Area Update (TAU) or the like sent to accesscontroller 122 via the RAN node to which the UE is attached. If the UE'slocation is determined to be stationary or approximately stationary fora specific geographic area identified by one or more cell-ID(s) and/orone or more eNB-ID(s) for one or more RAN node(s) then the UE can be‘pinned’ to the geographic area by the access controller and the UE canbe informed that it has been pinned to the geographic area. By ‘pinned’it is meant that an association can be stored for the UE and thespecific geographic area that links the UE to the cell-ID(s)/eNB-ID(s)for the specific geographic area in which the UE is determined to bestationary or approximately stationary. As referred to herein,information and/or parameters corresponding to the association of a UEto one or more cell-ID(s) and/or eNB-ID(s) can be referred to as ‘pinnedarea information’.

In various embodiments, cell-ID can include an Evolved UniversalTerrestrial Radio Access Network (E-UTRAN) Cell Global Identifier (ECGI)or the like as defined in 3GPP standards. In various embodiments, eNB-IDcan include a global identifier such as Global eNB-ID or Global HeNB-ID(e.g., for small cell deployments in which Home eNBs (HeNBs) aredeployed).

A UE can be informed that it has been pinned to a geographic area by theRAN node to which it is attached or by the access controller 122. In oneembodiment, for example, when a given UE (e.g., UE 112) moves fromactive to idle mode when the idle time expires at a given RAN node(e.g., RAN node 114), the UE can be informed by the RAN node that it hasbeen pinned to one or more cell-ID(s)/eNB-ID(s). In another embodiment,a UE can be informed via pinned area information that it has been pinnedto the one or more cell-ID(s)/eNB-ID(s) by an access controller (e.g.,access controller 122) in response to the access controller receivingmobility signaling (e.g., TAU, Service Request, etc.) from the UE. Insome embodiments, TAU Accept messaging can be enhanced to carry pinnedarea information to UE. In other embodiments, new mobility messaging canbe defined (e.g., for 4G or 5G deployments) to carry pinned areainformation to UE.

If a UE moves out of its current geographic area identified by one ormore cell-ID(s)/eNB-ID(s) (e.g., its pinned area) in idle mode, then theUE has to inform the network via signaling that is has moved out of itspinned area. In one embodiment, TAU Request messaging can be enhanced tocarry an indication that a UE has transitioned from its pinned area. Inanother embodiment, new mobility messaging (for 4G or 5G deployments)can be defined to carry an indication that a UE has transitioned fromits pinned area.

While a given UE remains in its pinned area the RAN node to which it isattached can maintain the S1-AP (e.g., access stratum) and S1-U contextfor the given UE. Thus, from the perspective of the core network 120,the UE can be considered as in the active mode. In various embodiments,UE context can include security context, authentication context,combinations thereof or the like.

Consider an operational example involving UE 112. If, for example,downlink data or control-plane signaling from the access controller 122for the UE arrives at the RAN node 114, then the RAN node can page theUE (if the radio resources are released) passing an indication to ‘onlyestablish the radio resources’ for the UE (e.g., to execute the radioresource establishment part of the Service Request procedure) ratherthan the initiating a full Service Request procedure for the UE.

Radio resources for the UE can then be established and the existingS1-AP and S1-U context can be used for transferring downlink and/oruplink control messages and data packets to/from the UE. The radioresources for the UE can also be established if the UE initiates ServiceRequest procedure. Thus, optimized Service Request procedure can beachieved via communication system 100 in accordance with at least oneembodiment.

Say, for example, that UE 112 is pinned to a particular geographic areaand moves out of the pinned area in idle mode. In such a case, when theUE moves out of its pinned area in idle mode it can inform the corenetwork 120 nodes that it has moved out of its pinned area. In variousembodiments, a given UE can inform an access controller (e.g., accesscontroller 122) and the RAN node (e.g., RAN node 114) to which it wasattached that it has moved out of a pinned area using an enhanced TAUwhich can be modified to include a reason or cause code identifying thatthe UE has moved out of its pinned area. In some embodiments, a newmessage can be defined such as, for example, a Pinned Area Update (PAU),which can be used to signal to an access controller that a given UE hasmoved out of its pinned area. For the operational example involving UE112, upon determining that the UE has moved out of the pinned area, theRAN node 114 releases the S1-AP and S1-U context (e.g., using the S1release procedure as currently defined in 3GPP specifications) for theUE so that the UE can be considered as in idle mode from the corenetwork perspective.

Thus, the system and method provided communication system 100 canprovide several advantages in various embodiments. For example, thesystem and method can provide optimizations in which reduced UE to RANnode signaling is needed during idle and active mode transitionprocedures when a given UE is within a pinned area, no RAN node todata-plane node signaling is needed when a given UE is within a pinnedarea, and/or no SGW-C to SGW-U is needed when a given UE is within apinned area (e.g., for a split C/U-plane architecture).

In summary, a signaling savings can be realized within the core networkand between UE and the core network due to frequent idle and active modetransition without changing the frequency of idle and active transitionsin accordance with various embodiments of communication system 100.Moreover, the system and method provided by communication system 100 canreduces the SGW-C to SGW-U signaling requirement, which can help inbuilding efficient split C/U-plane architectures.

Although not shown in FIG. 1, each of the element or node ofcommunication system 100 can include at least one processor, at leastone memory element and at least one storage, as discussed in furtherdetail herein. Further, aside from UE 112, any of the other elements ornodes of communication system 100 can be deployed as a physical hardwareelement or node or as a virtualized element or node. It should beunderstood that virtualized elements or nodes can be deployed in a SDNand/or Network Function Virtualization (NFV) architecture. As discussedherein, SDN/NFV allows network administrators, operators, etc. to managenetwork services through abstraction of lower level functionality into avirtualized network environment.

In general, RAN 110 may provide a communications interface between UE112, one or more elements and/or nodes of core network 120 and one ormore PDNs 130 for one or more 3GPP and/or non-3GPP access networks. Invarious embodiments, 3GPP access networks can include an LTE accessnetwork such as E-UTRAN, generally referred to as 4G or LTE/LTE-Advanced(LTE-A) and/or a 3GPP 5G access network. In various embodiments,non-3GPP access networks can include wireless local area networks(WLANs), such as Institute of Electrical and Electronic Engineers (IEEE)802.11 Wi-Fi networks, Worldwide Interoperability for Microwave Access(WiMAX) networks, Bluetooth™ networks, combinations thereof or the like.

In various embodiments, UE 112 can be associated with any users,subscribers, employees, clients, customers, electronic devices, etc.wishing to initiate a flow in communication system 100 via some network.In at least one embodiment, UE 112 is configured to facilitatesimultaneous Wi-Fi connectivity and cellular connectivity withincommunication system 100. The terms ‘user equipment’, ‘mobile node’,‘mobile station’ or ‘mobile device’ are inclusive of devices used toinitiate a communication, such as a computer, an electronic device suchas a parking meter, vending machine, appliance, Internet of Things (IoT)device, etc., a personal digital assistant (PDA), a laptop or electronicnotebook, a cellular telephone, an i-Phone™, i-Pad™, a Google Droid™phone, an IP phone, wearable electronic device or any other device,component, element, or object capable of initiating voice, audio, video,media, or data exchanges within communication system 100. UE 112 mayalso be inclusive of a suitable interface to a human user such as amicrophone, a display, a keyboard, or other terminal equipment. Asreferred to herein in this Specification, the terms ‘user’,‘subscriber’, ‘UE’ and ‘user/UE’ can be used interchangeably. It shouldbe understood that a user, or more particularly, a subscriber, can beassociated with the operation of a corresponding UE for one or morevoice and/or data sessions.

UE 112 may also be any device that seeks to initiate a communication onbehalf of another entity or element such as a program, a database, orany other component, device, element, or object capable of initiating anexchange within communication system 100. In certain embodiments, UE 112may have a bundled subscription for network access and applicationservices (e.g., voice), etc. In one embodiment, once the access sessionis established, the user can register for application services as well,without additional authentication requirements. Within communicationsystem 100, IP addresses (e.g., for UE or any other element incommunication system 100) can be assigned using DHCP, SLAAC, duringdefault bearer activation processes, or any suitable variation thereof.IP addresses used within communication system 100 can include IP version4 (IPv4) and/or IP version 6 (IPv6) IP addresses.

In various embodiments, RAN node 114 can be deployed as an eNB or HeNB(e.g., for 4G/LTE deployments), as a 5G radio node, combinations thereofor the like. In various embodiments, access controller 122 can bedeployed as an MME (e.g., for 4G/LTE deployments) or as a similarlyconfigured access control element for a 5G deployment. In variousembodiments, an MME or access controller can, in addition to thefeatures discussed for embodiments described herein, provide for UEtracking and paging procedures including, for example, retransmissions,tracking area list management, idle mode UE tracking, etc. An MME oraccess controller can further provide for UE bearer procedures includingactivation, deactivation and modification, SGW/SGW-U and PGW/PGW-Uselection for UE and authentication services.

In various embodiments, data-plane node(s) 124 can include one or moreSGWs and/or PDN Gateways (PGWs), Service Architecture Evolution (SAE)gateways, one or more SGW-Us, PGW-Us and/or one or more combinedS/P-GW-Us, for split C/U plane architectures, such as shown in theembodiment of FIG. 1. In various embodiments control-plane node(s) 126can include one or more SGW-Cs, one or more PGW-Cs and/or one or morecombined S/P-GW-Cs for split C/U plane architectures, such as shown inthe embodiment of FIG. 1. In general, An SGW or SGW-U is a data-planeelement that can provide functionality for managing user mobility andinterfaces with RAN nodes (e.g., eNBs, HeNBs, etc.). An SGW or SGW-Uservice function can also maintain data paths between RAN nodes andPGW(s) or PGW-U(s). A PGW or PGW-U service function typically providesIP connectivity access network (IP-CAN) session connectivity for UEs toone or more external PDN(s) (e.g., PDN(s) 130).

In various embodiments, core network 120 can include one or more otherelements, including, but not limited to: one or more Policy and ChargingRules Functions (PCRFs), one or more 3GPP AAA elements, one or more HomeSubscriber Servers (HSS), one or more SGW-Cs, one or more PGW-Cs (e.g.,for split C/U-plane architectures) combinations thereof or any otherelements or nodes as may be defined by 3GPP, Internet Engineering TaskForce (IETF), or similar organization.

Referring to FIG. 2, FIG. 2 is a simplified interaction diagram 200illustrating example details that can be associated with facilitatingoptimized idle and active state transitions in a network environment inaccordance with one potential embodiment of communication system 100.FIG. 2 includes UE 112, RAN node 114 and access controller 122. As shownin the embodiment of FIG. 2, once the UE is attached to the core network120 via RAN node 114 at 202, access controller 122 can monitor at 204(e.g., based on mobility messaging received from the UE) how long the UEstays within an area of one or a set of RAN node(s) in order to identifywhether the UE is relatively static (e.g., stationary or approximatelystationary) or mobile.

Upon determining that the UE is stationary, the access controller caninform the UE and the RAN node(s) that the UE has been pinned to a givenpinned area. For the embodiment shown in FIG. 2, the access controller122 can, in at least one embodiment, receive mobility signaling from theUE at 206 and can inform pinned area information for the pinned area toUE 112 and RAN node 114 at 208. In some embodiments, an accesscontroller (e.g., access controller 122) can inform a UE that it hasbeen pinned to an area using TAU Accept messaging that is enhanced tocarry pinned area information to UE. In other embodiments, new mobilitymessaging can be defined (e.g., for 4G or 5G deployments) to carrypinned area information to UE.

It is assumed for the embodiment shown in FIG. 2 that after a period oftime, the UE and/or RAN node(s) can detect radio level inactivity forthe UE at 210 and RRC is released for the UE via an RRC Connectionrelease at 212. The RAN node 114 keeps the access stratum (AS) and S1context for the UE even though the RRC is released and the UE keeps itsNAS association and releases only radio bearers as shown at 214. For thecore network (CN) node(s) (e.g., access controller 122, data-planenode(s) 124, control-plane node(s) 126), the UE mode is maintained asbeing in an active state as shown at 216.

Referring to FIG. 3, FIG. 3 is a simplified interaction diagram 300illustrating example details that can be associated with sendingdownlink data to UE 112 when the UE is in an RRC idle mode while thecore network 122 has associated the UE with being in an active mode inaccordance with one potential embodiment of communication system 100.FIG. 3 includes UE 112, RAN node 114, access controller 122 and aparticular data-plane node 124. The embodiment of FIG. 3 is assumed tofollow from the interactions shown in FIG. 2 in which the UE ismaintained as being in an active state in the CN node(s) at 302.

For the embodiment of FIG. 3, it is assumed that downlink data is sentat 304 from data-plane node 124 to the pinned RAN node 114. Uponreaching the RAN node 114, the RAN node determines at 306 that the UE isin an RRC idle state and that a page is needed for the UE to set upradio bearers for the UE. RAN node 114 also buffers the data at 306until the UE is transitioned into an active state. At 308, the RAN node114 pages the UE 112 and includes in the paging an indication that theUE is to only setup radio bearer(s) in response to the paging. At 310,the UE performs its RRC procedures, as defined in 3GPP TS 36.331,Section 5.3.3, and sets up radio bearer(s) with the RAN node 114. Oncebearer(s) setup is completed, the buffered data is forwarded to the UEfrom the RAN node 114 at 312.

Referring to FIG. 4, FIG. 4 is a simplified interaction diagram 400illustrating example details that can be associated with UE 112 shiftingto an RRC active state when the UE desires to send uplink data to RANnode 114 and/or a core network node or element in accordance with onepotential embodiment of communication system 100. FIG. 4 includes UE112, RAN node 114, access controller 122 and a particular data-planenode 124. The embodiment of FIG. 4 is assumed to follow from theinteractions shown in FIG. 2 in which the UE is maintained as being inan RRC active state in the CN node(s) at 402 while the UE is actually inan RRC idle state from the perspective of RAN node 114. At 404, it isassumed that the UE has uplink data to send and determines to transitionto an RRC active state.

At 406, RRC procedures, as defined in 3GPP TS 36.331, Section 5.3.3, arecarried out between the UE and the RAN node to setup bearer(s) for theUE without additional signaling between the access controller 122 andthe core network and/or within the core network itself (e.g., with oneor more data- and/or control-plane node(s)). At 408, the UE 112transitions to an RRC active state and follows existing 3GPP proceduresfor performing uplink data transfers, handover (HO), etc. For theembodiment shown in FIG. 4, uplink data for the UE 112 is sent todata-plane node 124 via RAN node 114 as shown at 410.

Thus, as shown in the embodiments illustrated in FIGS. 2, 3 and 4, thesystem and method provided by communication system 100 can, overall,reduce the total number of messages exchanged during the radio resourcerelease (e.g., transition to idle mode) and Service Request (e.g.,transition to active mode) procedures, which can take place around every2 mins per UE. This optimization can further help in achieving efficientsplit C/U-plane architectures.

One current solution is defined in 3GPP standards for optimizing idleand active mode transitions for cellular Internet of Things (CIoT)technology. Current CIoT procedures are outlined in 3GPP TS 23.401,Sections 5.3.4A and 5.3.5A. In general, procedures for CIoT provide thatwhen there is radio inactivity for a given UE, the given UE sends a RRCsuspend to the eNB to which it is connected. The eNB maintains theAccess Stratum context for the UE. However, the eNB sends an explicit S1signaling (S1AP UE Context Suspend Request) to the MME when the UE sendsits RRC suspend to the eNB and the MME sends an explicit Release AccessBearer Signaling to SGW. When the UE wants to resume data transmission,it sends an RRC Resume to the eNB, the eNB sends an explicit signaling(S1AP UE Context Resume Request) to the MME and the MME sends ModifyBearer Request to SGW. Thus, the net effect of the current CIoT solutiononly provides a savings in time that is taken between a UE servicerequest and radio bearer setup but there is no savings in signalingmessages with core network.

Embodiments of communication system 100 can provide for a reduced totalnumber of messaging for idle to active transitions in comparison to thecurrent CIoT solution provided in 3GPP standards. For example, as shownin the embodiment of FIG. 2, the number of signaling messages betweenthe RAN node and the access controller for an RRC release is zero;whereas for the current 3GPP CIoT solution, the number of signalingmessages is two involving an S1-AP UE Context Suspend Request andResponse. Further, the number of signaling messages between the accesscontroller and a mobility user plane anchor (e.g., in which data planenode 124 is an SGW/SGW-U) for an RRC release is zero; whereas for thecurrent CIoT solution, the number of signaling messages is two involvinga Release Access Bearer Request and Response with the SGW.

In another example, consider the embodiment shown in FIG. 3 involvingdownlink data to be sent to a UE when the UE is in an idle state fromthe perspective of the RAN node and is maintained as being in an activestate from the perspective of the core network node(s). For theembodiment shown in FIG. 3, the RAN node initiates paging to the UE;whereas, for the current 3GPP CIoT solution the access controllerinitiates paging. Further, the response to the paging for the solutionprovided by communication system 100 is only RRC and radio bearer(s)setup with the core network node(s) being unaffected; whereas, for thecurrent 3GPP solution, an RRC resume procedure is needed involving anS1-AP UE Context Resume Request and Response with the access controllerand a Modify Bearer Request and Response between the access controllerand the SGW.

Referring to FIG. 5, FIG. 5 is a simplified interaction diagram 500illustrating example details that can be associated with UE 112 movingout of a given pinned area in accordance with one potential embodimentof communication system 100. FIG. 5 includes UE 112, a source RAN node116, a target RAN node 118 and access controller 122. Source RAN node116 and target RAN node 118 can be other RAN nodes deployed within RAN110.

As shown in the embodiment of FIG. 5, the UE 112 can initiate a NASlevel mobility management procedure (e.g., TAU or the like) towardsaccess controller 122 via target RAN node 118 when the UE moves out ofthe coverage area of source RAN node 116 into the coverage area oftarget RAN node 118 at 502 to perform a handover (HO) to the target RANnode. For the embodiment of FIG. 5, the UE initiates a TAU Requesttoward access controller 122 at 504. The TAU can include a ‘reason’indicator that indicates the UE has moved out of its pinned area. In oneembodiment, a TAU Request message can be enhanced to carry such a reasonindicator as a bit or flag set for a particular Information Element (IE)within the message, which the access controller can parse to determinethat the reason for the TAU Request is because a given UE has moved outof its pinned area.

At 506, the access controller parses the reason indicator for the TAURequest message, removes the pinned area association for the UE and setsthe UE as being in an idle state for the perspective of the core network(CN) 120. At 508, the access controller sends a TAU Accept message tothe UE 112 including an indication that the pinned area has been removedfor the UE. Although TAU Request/Accept messages are shown in theembodiment of FIG. 5, it should be understood that any mobilitymessaging (existing or new) for 4G and/or 5G deployments can beconfigured to facilitate communicating pinned area transitions when a UEis in idle mode.

At 510, the UE can follow existing 3GPP procedures for idle modemobility procedures, Service Request procedures, etc. unless the UE isagain notified of being pinned to a particular geographic area, in whichcase the enhanced Service Request procedures, as discussed for variousembodiments described herein can be carried out. At 512, the accesscontroller 122 initiates an S1 release towards the source RAN node 116.At 514, the source RAN node 116 releases the stored access stratum andS1 context for the UE and, at 516, sends the access controller 122 anindication of the context release in an S1 release response.

The embodiment shown in FIG. 5 also differs from the current 3GPP CIoTsolution described in 3GPP TS 23.401. In particular, the optimizationsprovided via communication system 100 provide for a new pinned areaupdate procedure (e.g., using either an enhance TAU procedure or a newPAU procedure) when a given UE determines that it has left its pinnedarea, in which case the access controller tears down the saved accessstratum and S1 context for the UE in the old RAN node. For the current3GPP CIoT solution, access stratum and S1 context for a given UE aresuspended and transferred between RAN nodes across an X2 interface.Accordingly, there are several differences between the solution providedby communication system 100 and the current 3GPP CIoT solution.

Referring to FIG. 6, FIG. 6 is a simplified block diagram illustratingexample details that can be associated with UE 112 in accordance withone potential embodiment of communication system 100. UE 112 can includeat least one processor 602, at least one memory element 604, a storage606, at least one transmitter 608, at least one receiver 610 and atleast one antenna 614. At least one memory element 604 can includeinstructions for UE mobility logic 612.

In at least one embodiment, at least one processor 602 is at least onehardware processor configured to execute various tasks, operationsand/or functions of UE 112 as described herein and at least one memoryelement 604 is configured to store data, information, software and/orinstructions associated with UE 112 and logic configured for memoryelement 604. In various embodiments, storage 606 for UE 112 can beconfigured to store information and/or parameters associated withvarious operations as described herein including, but not limited to,storing pinned area information such as one or more cell-ID(s) and/oreNB-ID(s) received from a given access controller (e.g., accesscontroller 122) via a given RAN node to which the UE is attached (e.g.,RAN node 114) and/or storing any other information and/or parameters asdiscussed herein. In at least one embodiment, at least one transmitter608, at least one receiver 610 and at least one antenna 614 can operatein combination and/or with one or more other elements of UE 112 tofacilitate over the air communications with one or more RAN node(s) forvarious operations as described herein.

In at least one embodiment, UE mobility logic 612 can includeinstructions that, when executed by at least one processor 602, cause UE112 to perform one or more operations including, but not limited to:recognizing when the UE has been pinned to a particular geographic areaidentified by one or more cell-ID(s) and/or eNB-ID(s); recognizing whenthe UE moves out of a particular geographic area; initiating trackingarea update procedures or other mobility procedures (e.g., pinned areaupdate procedures) towards an access controller when the UE moves out ofa particular geographic area in an idle state in which the updateprocedures can include a reason for the update; setting up only radioresources (e.g., radio bearer(s)) in response to transitioning from anidle to active mode for the optimizations described herein; combinationsthereof or any other operations described for various embodimentsdiscussed herein.

Referring to FIG. 7, FIG. 7 is a simplified block diagram illustratingexample details that can be associated with RAN node 114 in accordancewith one potential embodiment of communication system 100. RAN node 114can include at least one processor 702, at least one memory element 704,a storage 706, at least one transmitter 708, at least one receiver 710,a network interface unit 712 and at least one antenna 714. At least onememory element 704 can include instructions for RAN node service requestlogic 716.

In at least one embodiment, at least one processor 702 is at least onehardware processor configured to execute various tasks, operationsand/or functions of RAN node 114 as described herein and at least onememory element 704 is configured to store data, information, softwareand/or instructions associated with RAN node 114 and logic configuredfor memory element 704. In various embodiments, storage 706 for RAN node114 can be configured to store information and/or parameters associatedwith various operations as described herein including, but not limitedto, storing pinned area information such as one or more cell-ID(s)and/or eNB-ID(s) received from a given access controller (e.g., accesscontroller 122) for a given UE (e.g., UE 112) that is attached to theRAN node; storing access stratum (AS) and S1 context information for agiven UE pinned to a particular geographic area that has transitioned toan idle state; and/or storing any other information and/or parameters asdiscussed herein. In at least one embodiment, at least one transmitter708, at least one receiver 710 and at least one antenna 714 can operatein combination and/or with one or more other elements of RAN node 114 tofacilitate over the air communications with one or more UE for variousoperations as described herein.

In various embodiments, network interface unit 712 enables communicationbetween RAN node 114, access controller 122, one or more data-planenode(s) 124, and/or any other RAN nodes (e.g., via a 3GPP X2 or similarinterface) that may be configured for communication system 100. In someembodiments, network interface unit 712 can be configured with one ormore Ethernet driver(s) and/or controller(s) or other similar networkinterface driver(s) and/or controller(s) to enable communications forRAN node 114 within communication system 100.

In at least one embodiment, RAN node service request logic 716 caninclude instructions that, when executed by at least one processor 702,cause RAN node 114 to perform one or more operations including, but notlimited to: storing pinned area information for a UE attached to the RANnode; recognizing when a UE has been pinned to a particular geographicarea identified by one or more cell-ID(s) and/or eNB-ID(s) anddetermining to store AS and S1 context information for the UE when it istransitioned to an idle state; determining to not perform signaling withcore network node(s) (e.g., access controller 122) when a pinned UE istransitioned to an idle state or an active state; combinations thereofor any other operations described for various embodiments discussedherein.

Referring to FIG. 8, FIG. 8 is a simplified block diagram illustratingexample details that can be associated with access controller 122 inaccordance with one potential embodiment of communication system 100.Access controller 122 can include at least one processor 802, at leastone memory element 804, a storage 806, and a network interface unit 808.At least one memory element 804 can include instructions for mobilitymanagement logic 810.

In at least one embodiment, at least one processor 802 is at least onehardware processor configured to execute various tasks, operationsand/or functions of access controller 122 as described herein and atleast one memory element 804 is configured to store data, information,software and/or instructions associated with access controller 122 andlogic configured for memory element 804. In various embodiments, storage806 for access controller 122 can be configured to store informationand/or parameters associated with various operations as described hereinincluding, but not limited to, storing geographic area information forone or more geographic area(s) that can each be identified by one ormore cell-ID(s) and/or eNB-ID(s); storing threshold time periodinformation that can be used in making pinned area determinations forone or more UE for one or more geographic area(s); storing pinned areainformation for one or more UE and/or storing any other informationand/or parameters as discussed herein.

In various embodiments, network interface unit 808 enables communicationbetween access controller 122, one or more RAN node(s) (e.g., RAN node114), one or more control-plane node(s) 126, one or more data-planenode(s) 124, and/or any other elements or nodes that may be configuredfor communication system 100. In some embodiments, network interfaceunit 808 can be configured with one or more Ethernet driver(s) and/orcontroller(s) or other similar network interface driver(s) and/orcontroller(s) to enable communications for RAN node 114 withincommunication system 100.

In at least one embodiment, mobility management logic 810 can includeinstructions that, when executed by at least one processor 802, causeaccess controller 122 to perform one or more operations including, butnot limited to: determining that a given UE is stationary orapproximately stationary in a particular geographic area identified byone or more cell-ID(s) and/or eNB-ID(s); storing pinned area informationfor one or more UE (e.g., UE 112); performing mobility signaling withone or more UE (e.g., informing UE that they have been pinned to an areavia an enhanced TAU Accept message or the like including such anindication); performing context release procedures; combinations thereofor any other operations described for various embodiments discussedherein.

In regards to the internal structure associated with communicationsystem 100, each of data-plane node(s) 124, control-plane node(s) 126,source RAN node 116, and target RAN node 118 may each also include arespective at least one processor, a respective at least one memoryelement and/or a respective at least one respective storage. Hence,appropriate software, hardware and/or algorithms are being provisionedin each of UE 112, RAN node 114, access controller 122, data-planenode(s) 124, control-plane node(s) 126, source RAN node 116, and targetRAN node 118 in order to facilitate various operations as described forvarious embodiments discussed herein to facilitate optimized idle andactive state transitions in a network environment. Note that in certainexamples, certain databases or storage (e.g., for storing informationassociated with idle and active mode transitions, pinned areainformation, etc.) can be consolidated with memory elements (or viceversa), or the storage can overlap/exist in any other suitable manner.

In one example implementation, UE 112, RAN node 114, access controller122, data-plane node(s) 124, control-plane node(s) 126, source RAN node116, and target RAN node 118 are network elements, which are meant toencompass network appliances, servers, routers, switches, gateways,bridges, loadbalancers, firewalls, processors, modules, or any othersuitable device, component, element, or object operable to exchangeinformation that facilitates or otherwise helps to facilitate variousoperations as described for various embodiments discussed herein in anetwork environment (e.g., for networks such as those illustrated inFIG. 1). In other embodiments, these operations and/or features may beprovided external to these elements, or included in some other networkdevice to achieve this intended functionality. Alternatively, one ormore of these elements can include software (or reciprocating software)that can coordinate in order to achieve the operations and/or features,as outlined herein. In still other embodiments, one or more of theseelements may include any suitable algorithms, hardware, software,components, modules, interfaces, or objects that facilitate theoperations thereof. This may be inclusive of appropriate algorithms,communication protocols, interfaces and/or standards, proprietary and/ornon-proprietary that allow for the effective exchange of data orinformation.

In various embodiments, UE 112, RAN node 114, access controller 122,data-plane node(s) 124, control-plane node(s) 126, source RAN node 116,and target RAN node 118 may keep information in any suitable memoryelement [e.g., random access memory (RAM), read only memory (ROM), anerasable programmable read only memory (EPROM), application specificintegrated circuit (ASIC), etc.], software, hardware, or in any othersuitable component, device, element, or object where appropriate andbased on particular needs. Any of the memory items discussed hereinshould be construed as being encompassed within the broad term ‘memoryelement’. Information being tracked or sent to UE 112, RAN node 114,access controller 122, data-plane node(s) 124, control-plane node(s)126, source RAN node 116, and/or target RAN node 118 could be providedin any database, register, control list, cache, or storage structure:all of which can be referenced at any suitable timeframe. Any suchstorage options may be included within the broad term ‘memory element’as used herein. Similarly, any of the potential processing elements,modules, controllers, and machines described herein should be construedas being encompassed within the broad term ‘processor’. Each of thenetwork elements and/or user equipment can also include suitableinterfaces for receiving, transmitting, and/or otherwise communicatingdata or information in a network environment.

Note that in certain example implementations, the operations as outlinedherein may be implemented by logic encoded in one or more tangiblemedia, which may be inclusive of non-transitory tangible media and/ornon-transitory computer readable storage media (e.g., embedded logicprovided in an ASIC, in digital signal processing (DSP) instructions,software [potentially inclusive of object code and source code] to beexecuted by a processor, or other similar machine, etc.). In some ofthese instances, memory elements can store data used for the operationsdescribed herein. This includes the memory elements being able to storesoftware, logic, code, or processor instructions that are executed tocarry out the activities described herein. A processor (e.g., a hardwareprocessor) can execute any type of instructions associated with data toachieve the operations detailed herein. In one example, the processorscan transform an element or an article (e.g., data, information) fromone state or thing to another state or thing. In another example, theactivities outlined herein to facilitate optimized idle and active modetransitions may be implemented with logic, which can include fixedlogic, programmable logic, digital logic, etc. (e.g., software/computerinstructions executed by a processor) and the elements identified hereincould be some type of a programmable processor, programmable digitallogic (e.g., a field programmable gate array (FPGA), a DSP processor, anEPROM, a controller, an electrically erasable PROM (EEPROM) or an ASICthat includes digital logic, software, code, electronic instructions, orany suitable combination thereof.

Note that in this Specification, references to various features (e.g.,elements, structures, modules, components, steps, operations,characteristics, etc.) included in ‘one embodiment’, ‘exampleembodiment’, ‘an embodiment’, ‘another embodiment’, ‘certainembodiments’, ‘some embodiments’, ‘various embodiments’, ‘otherembodiments’, ‘alternative embodiment’, and the like are intended tomean that any such features are included in one or more embodiments ofthe present disclosure, but may or may not necessarily be combined inthe same embodiments. Note also that a module, engine, controller,function, logic or the like as used herein this Specification, can beinclusive of an executable file comprising instructions that can beunderstood and processed on a computer, processor, combinations thereofor the like and may further include library modules loaded duringexecution, object files, system files, hardware logic, software logic,or any other executable modules.

It is also important to note that the operations and steps describedwith reference to the preceding FIGURES illustrate only some of thepossible scenarios that may be executed by, or within, the system. Someof these operations may be deleted or removed where appropriate, orthese steps may be modified or changed considerably without departingfrom the scope of the discussed concepts. In addition, the timing ofthese operations may be altered considerably and still achieve theresults taught in this disclosure. The preceding operational flows havebeen offered for purposes of example and discussion. Substantialflexibility is provided by the system in that any suitable arrangements,chronologies, configurations, and timing mechanisms may be providedwithout departing from the teachings of the discussed concepts.

Note that with the examples provided above, as well as numerous otherexamples provided herein, interaction may be described in terms of one,two, three, or four network elements. However, this has been done forpurposes of clarity and example only. In certain cases, it may be easierto describe one or more of the functionalities by only referencing alimited number of network elements. It should be appreciated thatcommunication system 100 (and its teachings) are readily scalable andcan accommodate a large number of components, as well as morecomplicated/sophisticated arrangements and configurations. Accordingly,the examples provided should not limit the scope or inhibit the broadteachings of communication system 100 as potentially applied to a myriadof other architectures.

As used herein, unless expressly stated to the contrary, use of thephrase ‘at least one of’, ‘one or more of’ and ‘and/or’ are open endedexpressions that are both conjunctive and disjunctive in operation forany combination of named elements, conditions, or activities. Forexample, each of the expressions ‘at least one of X, Y and Z’, ‘at leastone of X, Y or Z’, ‘one or more of X, Y and Z’, ‘one or more of X, Y orZ’ and ‘A, B and/or C’ can mean any of the following: 1) X, but not Yand not Z; 2) Y, but not X and not Z; 3) Z, but not X and not Y; 4) Xand Y, but not Z; 5) X and Z, but not Y; 6) Y and Z, but not X; or 7) X,Y, and Z. Additionally, unless expressly stated to the contrary, theterms ‘first’, ‘second’, ‘third’, etc., are intended to distinguish theparticular nouns (e.g., element, condition, module, activity, operation,etc.) they modify. Unless expressly stated to the contrary, the use ofthese terms is not intended to indicate any type of order, rank,importance, temporal sequence, or hierarchy of the modified noun. Forexample, ‘first X’ and ‘second X’ are intended to designate two Xelements that are not necessarily limited by any order, rank,importance, temporal sequence, or hierarchy of the two elements.

Although the present disclosure has been described in detail withreference to particular arrangements and configurations, these exampleconfigurations and arrangements may be changed significantly withoutdeparting from the scope of the present disclosure. For example,although the present disclosure has been described with reference toparticular communication exchanges involving certain network access,interfaces and protocols, communication system 100 may be applicable toother exchanges or routing protocols, interfaces and/or communicationsstandards, proprietary and/or non-proprietary. Moreover, althoughcommunication system 100 has been illustrated with reference toparticular elements and operations that facilitate the communicationprocess, these elements, and operations may be replaced by any suitablearchitecture or process that achieves the intended functionality ofcommunication system 100.

Numerous other changes, substitutions, variations, alterations, andmodifications may be ascertained to one skilled in the art and it isintended that the present disclosure encompass all such changes,substitutions, variations, alterations, and modifications as fallingwithin the scope of the appended claims. In order to assist the UnitedStates Patent and Trademark Office (USPTO) and, additionally, anyreaders of any patent issued on this application in interpreting theclaims appended hereto, Applicant wishes to note that the Applicant: (a)does not intend any of the appended claims to invoke paragraph (f) of 35U.S.C. Section 112 as it exists on the date of the filing hereof unlessthe words “means for” or “step for” are specifically used in theparticular claims; and (b) does not intend, by any statement in theSpecification, to limit this disclosure in any way that is not otherwisereflected in the appended claims.

What is claimed is:
 1. A method comprising: determining that a firstuser equipment (UE) of a plurality of UE is approximately stationary fora threshold period of time within a particular geographic area based, atleast in part, on a radio access network (RAN) node, wherein each UE ofthe plurality of UE is in communication with the RAN node via acorresponding first connection and wherein the RAN node is incommunication with a core network via a plurality of second connectionscorresponding to the plurality of UE that individually correspond to agiven UE of the plurality of UE; notifying the first UE that the firstUE has been associated with the particular geographic area; andtransitioning the first UE into an idle mode from an active mode,wherein the transitioning maintains the existing second connectionestablished between the RAN node and the core network for the first UEand releases the first connection between the RAN node and the first UE.2. The method of claim 1, further comprising: storing contextinformation for the first UE at the RAN node when the first UEtransitions to the idle mode.
 3. The method of claim 1, wherein theparticular geographic area is associated with at least one of: anidentity of the RAN node; and a cell identity for the RAN node.
 4. Themethod of claim 1, wherein determining that the first UE isapproximately stationary further comprises: monitoring mobilitysignaling from the first UE to determine an amount of time that thefirst UE has been attached to the RAN node; and comparing the amount oftime with the threshold period of time to determine when the amount oftime is greater than or equal to the threshold period of time.
 5. Themethod of claim 1, further comprising: notifying the core network whenthe first UE moves out of the particular geographic area.
 6. The methodof claim 5, wherein the notifying includes notifying an accesscontroller within the core network.
 7. The method of claim 6, whereinthe notifying is performed via Non-Access Stratum (NAS) signaling sentfrom the first UE to the access controller.
 8. The method of claim 1,further comprising: transitioning the first UE to an active state for atleast one of: sending downlink data or signaling to the first UE; andreceiving uplink data or signaling from the first UE.
 9. The method ofclaim 8, wherein the transitioning is performed without signaling thecore network that the first UE has been transitioned from the idle modeto the active mode.
 10. The method of claim 9, wherein the transitioningincludes only setting up radio bearers for the first UE.
 11. One or morenon-transitory tangible media encoding logic that includes instructionsfor execution that when executed by a processor, is operable to performoperations comprising: determining that a first user equipment (UE) of aplurality of UE is approximately stationary for a threshold period oftime within a particular geographic area based, at least in part, on aradio access network (RAN) node, wherein each UE of the plurality of UEis in communication with the RAN node via a corresponding firstconnection and wherein the RAN node is in communication with a corenetwork via a plurality of second connections corresponding to theplurality of UE that individually correspond to a given UE of theplurality of UE; notifying the first UE that the first UE has beenassociated with the particular geographic area; and transitioning thefirst UE into an idle mode from an active mode, wherein thetransitioning maintains the existing second connection establishedbetween the RAN node and the core network for the UE and releases thefirst connection between the RAN node and the first UE.
 12. The media ofclaim 11, the operations further comprising: storing context informationfor the first UE at the RAN node when the first UE transitions to theidle mode.
 13. The media of claim 11, wherein determining that the firstUE is approximately stationary further comprises: monitoring mobilitysignaling from the first UE to determine an amount of time that thefirst UE has been attached to the RAN node; and comparing the amount oftime with the threshold period of time to determine when the amount oftime is greater than or equal to the threshold period of time.
 14. Themedia of claim 11, the operations further comprising: notifying the corenetwork when the first UE moves out of the particular geographic area.15. The media of claim 11, the operations further comprising:transitioning the first UE to an active state for at least one of:sending downlink data or signaling to the first UE; and receiving uplinkdata or signaling from the first UE.
 16. The media of claim 15, whereinthe transitioning is performed without signaling the core network thatthe first UE has been transitioned from the idle mode to the activemode.
 17. The media of claim 16, wherein the transitioning includes onlysetting up radio bearers for the first UE.
 18. A system comprising: anaccess controller comprising at least one first memory element forstoring first data and at least one first processor that executesinstructions associated with the first data; a Radio Access Network(RAN) node comprising at least one second memory element for storingsecond data and at least one second processor that executes instructionsassociated with the second data; the access controller, when the atleast one first processor executes the instructions, being configuredto: determine that an first user equipment (UE) of a plurality of UE incommunication with the RAN node is approximately stationary for athreshold period of time within a particular geographic area based, atleast in part, on the first UE being connected to a core network via theRAN node, wherein each UE of the plurality of UE is in communicationwith the RAN node via a corresponding first connection and the RAN nodeis in communication with the core network via a plurality of secondconnections corresponding to the plurality of UE that individuallycorrespond to a given UE of the plurality of UE; notify the first UEthat the first UE has been associated with the particular geographicarea; and the RAN node, when the at least one second processor executesthe instructions, being configured to: transition the first UE into anidle mode from an active mode, wherein the RAN releases the firstconnection for the first UE and maintains the second connection for thefirst UE.
 19. The system of claim 18, wherein the access controller,when the at least one first processor executes the instructions todetermine that the first UE is approximately stationary, is furtherconfigured to: monitor mobility signaling from the first UE to determinean amount of time that the first UE has been attached to the RAN node;and compare the amount of time with the threshold period of time todetermine when the amount of time is greater than or equal to thethreshold period of time.
 20. The system of claim 18, wherein the RANnode, when the at least one second processor executes the instructions,is further configured to: transition the first UE to an active state forat least one of: sending downlink data or signaling to the first UE; andreceiving uplink data or signaling from the first UE.